Image illumination rendering system and method

ABSTRACT

The present invention facilitates efficient and effective image processing. A network can comprise: a first system configured to perform a first portion of lighting calculations for an image and combing results of the first portion of lighting calculations for the image with results of a second portion of lighting calculations; and a second system configured to perform the second portion of lighting calculations and forward the results of the second portion of the lighting calculations to the first system. The first and second portion of lighting calculations can be associated with indirect lighting calculations and direct lighting calculations respectively. The first system can be a client in a local location and the second system can be a server in a remote location (e.g., a cloud computing environment). The first system and second system can be in a cloud and a video is transmitted to a local system.

RELATED APPLICATIONS

This application claims the benefit of and priority to provisional application 61/819,330 (Attorney docket number NVI13308P) entitled “Computing Indirect Lighting in the Cloud for Interactive Display on a Client” filed May 3, 2013, this application is also a continuation in part and claims benefit and priority to application Ser. No. 14/058,132, entitled “System, Method, and Computing Program Product for Computing Indirect Lighting in a Cloud Network filed Oct. 18, 2013, which are both incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to the field of image presentation. In one embodiment, indirect lighting is computed in the cloud and amortized in real-time rendering.

BACKGROUND OF THE INVENTION

Electronic systems and circuits have made a significant contribution towards the advancement of modern society and are utilized in a number of applications to achieve advantageous results. Numerous electronic technologies such as digital computers, calculators, audio devices, video equipment, and telephone systems facilitate increased productivity and cost reduction in analyzing and communicating data, ideas and trends in most areas of business, science, education and entertainment. Frequently, these activities involve rendering and displaying images. However, rendering can involve complicated processing that occupies valuable resources and consumes time.

As user interfaces shift between a variety of platforms, (e.g., mobile phones, tablets, etc.) a number of applications (e.g., video, advanced games, graphics, etc.) face new challenges. Many popular traditional devices lack computational horsepower to render advanced effects such as global illumination, yet users typically expect continually increasing graphics quality. However, different platforms (e.g., laptops, tablets, cell phones, other mobile devices, etc.) usually have a number of limitations, (e.g., power limited, thermal limited, etc.). Many platforms are unlikely to reach desired rendering performance by relying only on Moore's Law alone. Some traditional Cloud graphics approaches attempt to offer a solution, replacing local client rendering with remote rendering. Some traditional systems attempt to offer advantages beyond improved image quality (e.g., virtualization; lower costs and piracy protection) and have started appearing commercially.

While design of rendering pipelines for PCs and consoles is reasonably well understood, design of Cloud pipelines is in its infancy. Prior cloud attempts, including commercial systems, typically use a very simple offload approach: which include synchronously map rendering for each user's frame to a single server. Remote offline-rendering systems like Autodesk360 may also attempt to do this, but the latency is irrelevant and not usually practically applicable to real-time focused applications. Conventional full-frame remote rendering attempts are often limited to simply running them within a virtual computing environment and streaming their output as video. FIG. 1 is a block diagram of a conventional approach in which all the indirect and direct light calculations are performed on a cloud. Some conventional cloud gaming approaches perform all the indirect and direct light calculations on a local client. FIG. 2 is a block diagram of a conventional approach in which all the indirect and direct light calculations are performed on a local client. Either way, the legacy attempts also typically have minimal or no amortization and scalability capability, often both critical requirements for economic Cloud deployments. In addition, traditional approaches also usually couple local device rendering latency to delays in network latency.

SUMMARY

The present invention facilitates efficient and effective image processing. In one embodiment, a network comprises: a first system configured to perform a first portion of lighting calculations for an image and combing results of the first portion of lighting calculations for the image with results of a second portion of lighting calculations; and a second system configured to perform the second portion of lighting calculations and forward the results of the second portion of the lighting calculations to the first system. The second portion of lighting calculations can be associated with indirect lighting calculations and the first portion of lighting calculations can be associated with direct lighting calculations. The first system can be in a local location and the second system can be in a remote location. For example, the first system can be a client and the second system can be a server. The second system can be in a cloud computing environment. It is also appreciated the first system and the second system can be in a cloud computing environment and a video including the image is transmitted to a local system.

In one exemplary implementation, the results of the second portion of the lighting calculations (e.g., indirect lighting results, etc.) can be amortized over a plurality of systems. For example, the results of the second portion of lighting calculations are transmitted to a third or more systems and combined with a plurality of results of other portions of lighting calculations performed by the third or more systems. It is also appreciated the lighting calculations can be implemented in a variety of approaches. The results of the second portion of lighting calculations include Voxel results and the Voxel results are combined with the first lighting calculation results on the first system. The results of the second portion of lighting calculations include irradiance map results and the irradiance map results are combined with the first lighting calculation results on the first system. The results of the second portion of lighting calculations include photon results and the photon results are combined with the first lighting calculations results on the first system.

DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and form a part of this specification, are included for exemplary illustration of the principles of the present invention and not intended to limit the present invention to the particular implementations illustrated therein. The drawings are not to scale unless otherwise specifically indicated.

FIG. 1 is a block diagram of a conventional approach in which all the indirect and direct light calculations are performed on a remote server.

FIG. 2 is a block diagram of a conventional approach in which all the indirect and direct light calculations are performed on a local client.

FIG. 3 is a flow chart of an exemplary method in accordance with one embodiment of the present invention.

FIG. 4 is a block diagram of exemplary architecture in which direct lighting and indirect lighting calculations are performed on different systems in accordance with one embodiment of the present invention.

FIG. 5 is a block diagram of exemplary architecture in which direct lighting calculations are performed on a client and indirect lighting calculations are performed on a cloud in accordance with one embodiment of the present invention.

FIG. 6 is a block diagram of exemplary architecture in which direct and indirect lighting calculations are performed on the could and results are amortized in accordance with one embodiment of the present invention.

FIG. 7 is a block diagram of another exemplary architecture in which indirect lighting calculations are performed on the could and results are amortized in accordance with one embodiment of the present invention.

FIG. 8 is a flow chart of an exemplary method in accordance with one embodiment of the present invention.

FIG. 9 is a block diagram of an exemplary computer system upon which embodiments of the present invention can be implemented.

FIG. 10 shows another exemplary architecture that incorporates an exemplary video processor or graphics processor in accordance with one embodiment of the present invention.

FIG. 11 shows a diagram showing the components of a handheld device 1100 in accordance with one embodiment of the present invention.

FIG. 12 is a block diagram of exemplary network 1200 performance of various lighting calculation operations in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION

Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with the preferred embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be obvious to one ordinarily skilled in the art that the present invention may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the current invention.

The present invention facilitates effective and efficient image processing. In one embodiment, portions of lighting calculations are split between different systems. In one exemplary implementation, indirect lighting calculations are performed on a remote system or device (e.g., in a server, in the cloud, etc.) and communicated to a local system or device (e.g., client, end user mobile device, etc.) which combines the indirect lighting results with results of direct lighting calculations that are performed on the local system. A first system can achieve greater end use display functionality and results by offloading portions of the lighting calculations to a second system. For example, a mobile device with relatively limited processing capability can provide better image presentations than would otherwise be available to just the mobile device alone. In addition, present approaches can facilitate conservation of resources by amortizing indirect lighting calculation results over a variety of different systems.

Indirect lighting rendering typically involves consumption of significantly more processing resources than direct lighting rendering. The computation of indirect light is often too expensive for weaker or smaller clients (e.g., phones, tablets, PCs with lesser performance capabilities, etc.). Present approaches in which indirect lighting calculations are performed on a stronger or larger server and the results are forwarded to the client for to be composed with direct light on the client enables richer graphics capabilities and presentations on the otherwise weaker or lower performance clients.

A variety of lighting strategies can be implemented (e.g., offline and near-real time illumination path approaches, light map approaches, photon map approaches, cone/beam tracing approaches, voxelized transport approaches, etc.). In one embodiment, direct lighting and indirect lighting are not synchronized and indirect lighting associated algorithms and calculations can be run asynchronously in the cloud. For example, indirect lighting from a car might lag behind the direct lighting (which includes the shadow). It is not necessarily intuitive that this asynchrony is visually acceptable, but numerous present implementation tests confirm that it is generally visually acceptable for relatively large time gaps (e.g., ½ second, etc.) between direct and indirect lighting. In one exemplary implementation, a present approach is extremely beneficial for cloud gaming where hard to control lag is a key practical issue.

A system implementing present approaches may be configured to include many useful features and characteristics. For example, the system can be configured to compute shared indirect lighting in the cloud using a shared GPU rather than a GPU or virtual GPU per client. A number of streaming approaches can be implemented to improve latency. The system can be configured to: stream batches of photons to reduce latency and improve efficiency of photon processing; stream voxel blocks to reduce latency; stream [irradiance] light maps encoded as H.264 video; and use H.264 video to compress non-visual data. The system can be configured to predict future lighting conditions by dead reckoning and physical movement simulation to reduce latency, so the client can predict where the lighting changes will be. Many-to-many sharing of lighting servers and direct illumination clients can be implemented. Fading transitions between streamed indirect lighting data updates can also be implemented.

FIG. 3 is a flow chart of an exemplary method 300 in accordance with one embodiment of the present invention. In one embodiment, a first system is configured to perform operations associated with blocks 310 and 340 and a second system is configured to perform operations associated with blocks 320 and 330.

In block 310, a first portion of lighting calculations for an image is performed. In one embodiment, the first portion of lighting calculations is associated with direct lighting calculations for the image.

In block 320, a second portion of lighting calculations for an image is performed. In one embodiment, the second portion of the lighting calculations is associated with indirect lighting calculations for the image.

In block 330, the results of the second portion of the lighting calculations are forwarded to another system. In one embodiment, the results of the second portion of the lighting calculations are forwarded from the second system to the first system. In one exemplary implementation, the results of the second portion of the lighting calculations are forwarded from the second system to a plurality of systems.

In block 340, results of the first portion of lighting calculations for the image are combined with results of the second portion of lighting calculations. In one embodiment, the image is rendered and displayed based upon the combination of the results of the first portion of lighting calculations and the results of the second portion of lighting calculations.

It is appreciated that a first portion and second of lighting calculations can be directed to a variety of lighting aspects and the indication of direct lighting and indirect light is just one of many. In one embodiment, direct lighting is considered to be light that comes directly from a light source to a viewed point or surface (which can also produce familiar shadows when the light is blocked). In one embodiment, indirect light (also sometimes referred to as bounce light) is light that bounces off or is reflected off another surface and illuminates the point or surface being viewed. For example, reflected light on the bottom of a person's chin when the sun is above can be considered indirect light.

It is appreciated that method 300 is compatible with a variety of illumination algorithms or calculation approaches (e.g., voxel, irradiance maps, photon, etc.). In one embodiment, the results of the second portion of lighting calculations include Voxel results and the Voxel results are combined with the first portion of lighting calculation results on the first system. Voxel based indirect lighting computation can involve storing indirect light values corresponding to a 3D volume as voxels (e.g., a 3D lattice, etc.). The second portion of lighting calculations results include irradiance map results and the irradiance map results are combined with the first portion of lighting calculation results on the first system. Algorithms can be applicable to light maps where the indirect light values are stored as textures (e.g., images, etc.). In one exemplary implementation, the results of the second portion of lighting calculations include photon results and the photon results are combined with the first lighting calculations results on the first system. Photon approaches can involve storing the indirect light as 3D points. Additional description of various illumination algorithms or calculation approaches is included in subsequent sections of the detailed description.

It is appreciated that method 300 can be implemented in a variety of environments and network configurations. In one embodiment, the first system is in a local location and the second system is in a remote location. The first system can be a client and the second system can be server. All or some of the systems can be included in a cloud computing environment or architecture. It is also appreciated that network configurations can include additional systems. In one embodiment, the results of the second portion of lighting calculations are forwarded to a third or more systems and combined with a plurality of results of other portions of lighting calculations performed by the third or more systems. Present approaches are readily scalable for implementation with numerous devices (e.g., 10 end-user devices, 50 end user devices, 100 end user devices, 5 servers, 2 physical servers configured as one virtual server, etc.).

FIG. 4 is a block diagram of exemplary architecture 400 in accordance with one embodiment of the present invention. Architecture 400 includes system 410, system 420, system 430, and system 450. System 410 performs indirect lighting operations 415 and game logic operations 419. Indirect lighting result information 475, 485 and 495 is forwarded to systems 420, 430 and 450 respectively. System 420 performs direct lighting operations 423 and game logic operations 424. System 430 performs direct lighting operations 433 and game logic operations 434. System 450 performs direct lighting operations 453 and game logic operations 454. Systems 420, 430 and 450 forward User Interface (UI) event information 471, 481 and 491 respectively to system 410. System 410 forwards game state information 472, 482, and 492 to systems 420, 430, and 450 respectively. Systems 420, 430 and 450 combine the indirect lighting operations results with the direct lighting operation results during image rendering.

FIG. 5 is a block diagram of exemplary architecture 500 in accordance with one embodiment of the present invention. In one embodiment, architecture 500 is similar to architecture 400 in which system 410 is similar to cloud component 510 and systems 420, 430 and 450 are similar to client components 520, 530 and 550 respectively. Cloud component 510 performs indirect lighting operations 515 and game logic operations 519. Indirect lighting result information 575, 585 and 595 is forwarded to client components 520, 530 and 550 respectively. Client component 520 performs direct lighting operations 523 and game logic operations 524. Client component 530 performs direct lighting operations 533 and game logic operations 534. Client component 550 performs direct lighting operations 553 and game logic operations 554. Client components 520, 530 and 550 forward UI events 571, 581 and 591 respectively to cloud 510. Cloud 510 forwards game state 572, 582, and 592 to client components 520, 530, and 550 respectively. Systems 520, 530 and 550 combine the indirect lighting operations results with the direct lighting operation results during image rendering.

FIG. 6 is a block diagram of exemplary architecture 600 in accordance with one embodiment of the present invention. Architecture 600 includes cloud 610, client 620, client 630, and client 650. Cloud 610 performs indirect lighting operations 615, game logic 619, direct lighting operations 616, direct lighting operations 617, direct lighting operations 618, video encoding 611, video encoding 612 and video encoding 613. Direct lighting operations 616 and video encoding 611 are associated with Client 620. Direct lighting operations 617 and video encoding 612 are associated with Client 630. Direct lighting operations 618 and video encoding 613 are associated with Client 650. Clients 620, 630 and 650 perform video decoding operations 621, 631 and 651 respectively. Clients 620, 630 and 650 forward UI events 671, 681 and 691 respectively to cloud 610. Cloud 610 forwards game state 672, 682, and 692 to clients 620, 630, and 650 respectively. Cloud 610 amortizes or shares the results of indirect lighting operations 615 by combining them with direct lighting operations 616 results, direct lighting operations 617 results, and direct lighting operations 618 results during image rendering for corresponding clients 620, 630 and 650 respectively.

FIG. 7 is a block diagram of exemplary architecture 700 in accordance with one embodiment of the present invention. Architecture 700 includes cloud 710, client 720, client 730, and client 750. In one embodiment, Architecture 700 is similar to architecture 600 in which Cloud 610 is similar to Cloud 710. Cloud 710 includes Systems 701, 702 and 703. System 701 performs indirect lighting operations 715 and game logic 719. System 702 performs direct lighting 716 and video encoding 711, which are associated with client 720. System 702 also performs direct lighting 717 and video encoding 712, which are associated with client 720. System 703 performs direct lighting 718 and video encoding 713 which are associated with client 750. Clients 720, 730 and 750 perform video decoding operations 721, 731 and 751 respectively. Clients 720, 730 and 750 forward UI events 771, 781 and 791 respectively to system 710. Cloud 710 forwards game state 772, 782, and 792 to clients 720, 730, and 750 respectively. Cloud 710 amortizes or shares the results of indirect lighting operations 715 by combining them with direct lighting operations 716 results, direct lighting operations 617 results, and direct lighting operations 618 results during image rendering for corresponding clients 720, 730 and 750 respectively.

It is appreciated the present approach can be readily implemented in a variety of network configurations. In one embodiment, servers are abstracted into the cloud. The cloud can include a plurality of servers with reliability similar to a utility and similarly commoditized and abstracted, from both the end user's and developer's perspective. In one exemplary implementation, the cloud introduces a heterogeneous set of computers, connected by fast interconnect, that offload shared or overflow computations from user devices. The networks can have latency and bandwidth that vary over time and geographical region. Present approaches can enable mapping of various global illumination feature calculations (e.g., indirect lighting, etc.) into existing and future cloud architectures. They are readily implemented with different network links and partitions of work between components in accordance with latency and bandwidth characteristics of different algorithms.

In addition to being readily implemented in a variety of network configurations the present approaches is also compatible with a variety of illumination algorithms or calculation approaches. Unlike some conventional remote rendering attempts which stream video and may incidentally send graphics commands (and might be considered as placing a network between a CPU and a GPU), the present approach places links between algorithmic components.

With reference again to a voxel approach, Voxels typically represent indirect irradiance as a directionally varying, low-dimensional quantity on a sparse 3D lattice. Reconstructing indirect light from voxels is relatively inexpensive compared to other approaches (although can be more expensive than from 2D textures). However, the usually large memory footprint of the voxel grid makes transmission of voxels directly to users inconvenient or unpractical. Instead, lighting can be reconstructed in the cloud and fully-rendered frames streamed to clients or users. The voxel approach multi-resolution representation facilitates the use of lower resolutions for fast objects or camera movements and when high quality solutions are not yet available. With a world-space voxel structure, computation can be more precisely focused to compute indirect light where visible, and multiple GPUs inside a server can easily exchange data to collaborate. The implementation of the voxel approach with rendering of full frames on a server facilitates bandwidth reduction to the end user. In one embodiment, it distributes the rendering pipeline across three GPUs with two splits; one split between indirect and direct, and one split between direct and display. The voxel approach can be considered a first step from traditional full-frame streaming with dedicated resources per user to a future in which computation is amortized over multiple users on the server side.

The voxel global illumination approach can build on sparse-octree global illumination, and can be thought of as a multi-resolution octree irradiance cache or a 3D light map. Using this approach avoids constructing surface parameterizations, which can be a key advantage. In the cloud, indirect light is gathered to a directionally varying irradiance sample at the multi-resolution voxels. To reconstruct indirect light, cones are traced through this voxel grid (similar to a traditional photon map final gather) to generate view-dependent indirect light for each client. This view-dependent reconstruction also occurs in the Cloud, though it can use a separate GPU from the per-voxel sampling.

In one embodiment, the voxel approach includes various steps or operations. Scene geometry can be voxelized (either offline or dynamically). Light can be injected into a sparse voxel grid, which can also be filtered. Cones can be traced through the grid to propagate lighting. The approach can use cone traced results to generate fully-illuminated frames. Each frame can be encoded (e.g., H.264 encoding, etc.) and sent to an appropriate client. The frames can also be decoded (e.g., Decode H.264, etc.) on the client and displayed.

While basic voxel lighting may run well on high-end PCs, it is often much more difficult to implement on various other platforms. The present approach facilitates mapping it to the Cloud and making results available on the various other platforms. While view independent, the light injection and propagation steps can require substantial resources. To facilitate amortization of computations over many clients, the present approach can propagate light via cone tracing to a view independent, per-voxel representation, rather than per-pixel output. After cone tracing, querying the resulting view-independent voxel irradiance cache can occur quite efficiently. However, in some implementations, shipping a large voxel grid over a network for client reconstruction can be undesirable. Instead, the present approach can include transferring of the voxels to another Cloud GPU to reconstruct, compress, and send fully rendered frames to clients. In one embodiment, the voxel approach or algorithm uses one GPU (which can be called the global illumination GPU) to generate view-independent data plus another GPU (which can be called the final frame GPU) to generate the view-dependent frames sent to clients. The final frame GPU can be “smaller” (e.g., less resources, less capability, less performance, etc,) than the global illumination GPU.

In one embodiment, to utilize fast GPU-to-GPU transfers, global illumination and final frame GPUs reside in a single server. However, a voxel representation can include a significant data size. Several strategies can be implemented to compress data for efficient transfer; including: bricking voxels, with per-brick compaction; wavelet voxel encoding for finer octree levels; restricting GPU-to-GPU transfers to a minimal octree cut; asynchronous updates with DMA transfers between GPUs; and progressive, frequency-dependent decompression. Transfers can be sped up by reducing the amount and precision of voxel data, limiting transmissions to important voxels, and using asynchronous communication. Reconstruction can be sped up (and further reduce bandwidth) by computing full resolution only in areas requiring high frequency detail.

In one embodiment, design spectra for implementation of a present voxel approach includes various behavior and characteristics. Client power consumption can be minimal. For example, minimal power consumption for support of client H.264 decode. Computations can appear synchronous to a client, but occur asynchronously on two GPUs in the Cloud. Bandwidth and latency similar to VoIP and bandwidth of video-streaming can be utilized. Multi-resolution octree enables progressive, coarse-to-fine updates. In one exemplary implementation, pipelines are updated to handle voxels.

Referring again to irradiance maps. Irradiance Maps typically represent indirect irradiance in texture light maps. Typically these textures are static and computed offline during authoring. In one embodiment, indirect light is gathered at texels interactively in the cloud using ray tracing. Geometry can be parameterized to allow a mapping of geometry to individual irradiance map texels. Although commonly done, producing a parameterization is laborious and difficult. A client receiving irradiance maps typically decodes transmitted H.264 data and combines with locally-computed direct lighting, so relatively weak user hard-ware often suffices. As maps may be broadcast to multiple users, computation often readily amortizes. Incrementally adding multi-bounce lighting can be relatively straightforward by gathering from the prior frame's irradiance map. This strategy usually maps well to current game engines because it minimizes required network bandwidth and changes to the under-lying client-side renderer.

The present approach irradiance maps can often seamlessly fit into existing engines with directional light map illumination (e.g., such as Unreal Engine 3 and the Source Engine, etc.). Traditional systems attempt to use static, offline “pre-baked” irradiance maps. The present approach can leave the local device renderer unmodified. However, the present approach can also extend the system to stream dynamic textures for the illumination data. This can facilitate keeping the client simple. In one embodiment, a present approach can be conveniently and efficiently implemented with minimal new resources or logic for dynamic indirect light (e.g., a network decoder to interpret incoming irradiance maps).

In one embodiment, as long as the server outputs compressed irradiance maps with the required performance, it can use a variety of baking algorithms. In one exemplary implementation, the present approach can be implemented with two irradiance map servers. A first irradiance map server gathers irradiance naively at each texel using an OptiX-based ray tracer. The second irradiance map server (which can be more sophisticated and efficient that the first server) first decomposes the irradiance map into coarse basis functions. In one exemplary implementation, the second irradiance map server only gathers illumination once per basis. The present irradiance map approach can require an order of magnitude fewer rays for comparable performance, accelerating computation sufficiently to allow multiple updates of the entire irradiance map per second.

In both cases, irradiance maps can be compressed using a hardware H.264 encoder prior to transmission and decompressed on the client-side with an optimized CUDA decoder. While more sophisticated compression to mitigate artifacts can be used (as H.264 encoding was not designed for the myriad discontinuities in irradiance maps). However, the masking effects of texturing and ambient occlusion on the low-frequency indirect illumination sufficiently mitigates the visual impact of compression artifacts, and the benefits of leveraging the highly performance and power efficient H.264 encoder often outweigh the potential advantages of a custom irradiance map encoder.

In one embodiment, an irradiance map system can implement various steps or operations, including: offline generation of global unique texture parameterization; offline clustering of texels into basis functions; gathering indirect light at each basis function (or texel); reconstructing per-texel irradiance from basis functions; encoding irradiance maps to H.264; transmitting to client; decoding on the client; and rendering direct light while using irradiance map for indirect light. In one exemplary implementation, at every iteration a texture-space deferred shading pass is performed over the irradiance map (e.g., using a texture space G-buffer and current irradiance maps as input). OptiX can be used to per form a gather of indirect light, either at every valid texel or once per basis function. A raster can be used to offload computation of direct light in texture space, often improving performance. Numerous other approaches can be implemented to reduce server costs for irradiance map creation. Using cluster bases can significantly reduce the number of gather points. As a process, mutually visible texels (e.g., not separated by walls, etc.) can be clustered with similar normals. In one exemplary implementation, each basis has a radius of influence, and when gathering at basis functions, up to 8 bases are blended to reconstruct per-texel irradiance.

In one embodiment, each irradiance map update gathers a single bounce of indirect light. Multi-bounce lighting can be achieved by consulting the prior irradiance map when gathering subsequent irradiance maps. High memory coherency for rays traced in parallel can be facilitated by: reordering hemispherical QMC samples into clusters of coherent rays; tracing clustered rays in parallel (in a warp) rather than sequentially; and avoiding complex materials during irradiance map creation. To eliminate popping due to sudden illumination changes or un-expected network latency, client-side temporal filtering can be achieved using an exponentially weighted average over multiple irradiance maps

In one embodiment, design spectra for implementation of a present irradiance map approach includes various behavior and characteristics. Moderate client power is needed (e.g. to render direct light plus decoded H.264 irradiance map). New irradiance maps can be computed asynchronously and incorporated on a client as they arrive. Bandwidth equivalent to streaming can be used. In one exemplary implementation, latency is tolerant with client side filtering. Progressive refinement is utilized in which path length is increased by one each iteration (e.g., by seeding with the current irradiance map, etc.). It is also possible to use hierarchical basis functions to increase resolution with each iteration. In one embodiment, client rendering pipelines use irradiance maps to increase resolution with each iteration. In one embodiment, client rendering client rendering pipelines use irradiance maps and are readily integrated with conventional client rendering pipeline schemes.

With reference now to photon tracing approaches. Photons represent indirect light as point sampled particles. As photons may have independent lifetimes, intelligent management allows reuse between frames and multiple users. This also allows parallelization over multiple cloud GPUs and the ability to progressively update photons in batches for a more immediate response to changes in lighting. Client light reconstruction can be relatively expensive, often requiring recent GPUs for interactivity. However, photons put few demands on scene authoring, typically not requiring either parameterization nor voxelization. Using photons can offer a tradeoff requiring higher user hardware computation in exchange for high image quality and reduced authoring costs. This may be considered an aggressive approach. However, it can have the potential for a high quality, especially for glossy indirect reflections.

It is appreciated that full frames can be rendered on the server using irradiance maps or photons instead of voxels. In one embodiment a separate server process launches and renders full frames when a mobile client connects to the server. However, for sufficiently powerful clients, those methods can present a lower bandwidth, lower-latency solution if the client participates in rendering. In one embodiment, the thrust of the voxel strategy is on distributing the indirect and direct light computation between two server-side GPUs that do not share an address space but do share a high-performance bus. In one exemplary implementation, streaming of the final frames to the client can be configured similar to existing solutions and independent of the indirect light strategy.

In one embodiment, a standard photon tracer is implemented via a Cloud-based OptiX engine. The photons are compacted and compressed for transmission to the clients, which then render indirect illumination from them via a screen-space scatter approach, rather than a traditional final gather. To produce timely updates, photons are continually traced in small batches and transmitted based on completion rather than waiting for all photons in the scene. This allows convergence in time, similar to frameless rendering or real-time path tracing approaches. Because indirect light often changes gradually, in many cases the artifacts resulting from this are hard to perceive while the short update time between a scene change and a new illumination being sent to the client is usually beneficial.

In one embodiment, a photon map system can implement various steps or operations, including: tracing photons using Cloud-based ray tracer; transferring a bit-packed encoding of photons to clients; expiring old photon packets on a client; replacing with new ones; scattering photons into client view to accumulate indirect light; and summing indirect light with locally-computed direct illumination.

In one embodiment, a key feature of the present approach pipeline is photon hatching. A global parameter controls photon count per emitted watt of illumination, which sets total photons per iteration. These are grouped into fixed-sized batches, with photons in each batch emitted from one light. To ensure full GPU utilization and avoid noise for dim lights, additional photons are added (and renormalized) so each light emits an integer number of batches. Each photon stores direction, power, position, radius, and normalization factors packed into a 20-byte structure. Normalization can be deferred to the client to preserve precision. This precision can be ignored to regain some network bandwidth.

Batching can have many advantages. Common ray origins and directions can dramatically improve memory coherence (and performance) when traversing ray acceleration structures. Tracing and transmitting small batches also usually reduces latency between interaction and first visible change. Fixed batch sizes can simplify memory allocations and transfers at multiple stages in the pipeline. In one embodiment, when lighting changes, identifying stale photons is straightforward, as batches directly correspond to specific lights; and only photons whose corresponding light changed are reshot. In one exemplary implementation, for dynamic geometry, only photon batches that interact with this geometry need updating.

Once photons reach the client an image space splatting approach is used to gather indirect light. A 2D bounds method can be used. This uses a deferred render pass, which expands photons to a polygonal approximation of their area of influence. A photon density estimation kernel runs over covered pixels, with results output to a low resolution additive accumulation buffer. A bilateral upsample can be supplied to get a full-resolution indirect illumination buffer. This approach can be a relatively fastest approach and can be easily incorporated into a renderer.

In one embodiment, design spectra for implementation of a present photon approach includes various behavior and characteristics. Relatively powerful clients are utilized for photon reconstruction requires powerful client. Photons can be computed asynchronously and incrementally incorporated on the client-side. In one exemplary implementation high bandwidth is utilized due to photon size and progressive nature provides good latency tolerance. Subset of photons can be updated, including just those for dynamic lights or objects. Memory use is reasonable and reconstruction is readily implemented.

FIG. 12 is a block diagram of exemplary network 1200 in accordance with one embodiment of the present invention. Network 1200 includes cloud 1210 and client 1220 and facilitates utilization of a variety of global illumination algorithms, including a voxel approach, an irradiance map approach and a photon approach. The voxel approach includes voxel injection operations 1211, voxel cone trace operations 1212, voxel interpolation with direct and post operations 1213, decode operations 1224 and display operation 1225. The irradiance map approach includes OptiX ray trace operations 1214, reconstruct irradiance map operations 1215, direct and post operations 1227 and display operations 1228. The photon approach includes OptiX photon operations 1217, voxel cone trace operations 1221, direct and post operations 1222 and display operations 1223. Cloud 1210 performs voxel injection operations 1211, voxel cone trace operations 1212, voxel interpolation with direct and post operations 1213, OptiX ray trace operations 1214, reconstruct irradiance map operations 1215, and OptiX photon operations 1217. Client 1220 performs decode operations 1224, display operation 1225, direct and post operations 1227, display operations 1228, voxel cone trace operations 1221, direct and post operations 1222, and display operations 1223. While there can be different bandwidth and latency between the different operations, in one embodiment the network can be configured so that network connections are located at points with minimal bandwidth requirements. For example, network 1200 can be configured so that network connections are located between voxel interpolation with direct and post operations 1213 and decode operations 1224; between reconstruct irradiance map operations 1215 and direct and post operations 1227; and between OptiX photon trace operations 1217 and voxel cone trace operations 1221. In one embodiment, display 1225 is associated with a smart phone end use system, display 1228 is associated with a laptop computer end use system and display 1223 is associated with a high end personal computer (PC) end use system and a different global illumination algorithm (e.g., voxel, irradiance map, or photon) is utilized in accordance with the type of end use system.

FIG. 8 is a flow chart of an exemplary method 800 in accordance with one embodiment of the present invention. In one embodiment, resources at a local location are configured to perform operations associated with blocks 810 and 840 and resources at a remote location are configured to perform operations associated with blocks 820 and 830.

In block 810, a first portion of lighting calculations for an image are performed at a local location. In one embodiment, the first portion of lighting calculations is associated with direct lighting calculations. The local location can include a client.

In block 820, a second portion of lighting calculations for an image are performed at a remote location. In on embodiment, the second portion of lighting calculations is associated with indirect lighting calculation. The remote location can include a server. In one exemplary implementation, the remote location is included in a cloud computing environment.

In block 830, results of the first portion of the lighting calculations are communicated to the local location. The results of the second portion of lighting calculations can be communicated to a plurality of other locations.

In block 840 results of the first portion of the lighting calculations are combined with results of the second portion of the lighting calculations at the local location. The results of the second portion of lighting calculations can be amortized among a plurality of other locations.

In one embodiment, a present approach for computing indirect lighting in the cloud supports real-time rendering for interactive 3D applications on a user's local device. A traditional graphics pipeline (e.g., associated with a single device, etc.) can be mapped onto a distributed system or architecture. In one exemplary implementation, there are various differences from conventional single device approaches. Mapping the indirect light calculations onto the cloud introduces potential asymmetry between computational resources available at the cloud and local device side or the pipelines. In a multi user environment, a cloud solution can amortize “expensive” global illumination operations across multiple users. There can also be differences in latency and bandwidth between some pipeline stages. For example, differences between single device hardware memory bus characteristics and network connections can contribute to differences in latency and bandwidth. It is appreciated that present approaches facilitate flexible implementation of tradeoffs in different partitions of the global illumination workload between cloud and local devices, with consideration or how available network and computational power/performance influence design decisions and image quality. Consideration can also be given to the characteristics and functionality of the end user devices, including: lower power/performance devices (e.g., that can stream video, etc.); medium power/performance devices that can also perform basic rendering (e.g., z-buffer, direct light, texture mapping, etc.); and higher power/performance devices that can also perform at least moderately sophisticated work beyond basic graphics.

It is also appreciated, that there are significant differences between conventional remote rendering attempts and present approaches. As described above, present approaches facilitate various implementations that accommodate different considerations. The considerations can include consideration of implementation details due to differences between types of data sets being processed (e.g., differences in data sets associated with real time interactive video games versus scientific visualization applications, etc.) and the impact of latency and bandwidth (e.g., focus on accuracy rather than latency, etc.). Conventional attempts at parallel rendering typically try to emphasize utilization and not latency or amortization over users, giving rise to significantly different design space and bottlenecks that do not extend well to real time or interactive cloud rendering. Present approaches are not necessarily limited to specialized contexts (e.g., multi-node ray tracers, VR CAVEs, etc), but rather facilitate convenient and efficient implementation to a wide variety of applications (e.g., industry-and-systems oriented approach, deployment on a various scales such as consumer scale, etc.).

In one embodiment, coarse synchronization between direct and indirect light is utilized and latency from a distributed cloud architecture is acceptable. Present approaches facilitate direct lighting rendering on a local device enabling more immediate response to user input, irrespective of network conditions. In one exemplary implementation, the indirect illumination is view-independent and more robust to temporary network outages. The last known illumination can be reused (e.g., until network connectivity is restored, etc.).

With reference to FIG. 9, a block diagram of an exemplary computer system 900 is shown, one embodiment of a computer system upon which embodiments of the present invention can be implemented. Computer system 900 includes central processor unit 901, main memory 902 (e.g., random access memory), chip set 903 with north bridge 909 and south bridge 905, removable data storage device 904, input device 907, signal communications port 908, and graphics subsystem 910 which is coupled to display 920. Computer system 900 includes several busses for communicatively coupling the components of computer system 900. Communication bus 991 (e.g., a front side bus) couples north bridge 909 of chipset 903 to central processor unit 901. Communication bus 992 (e.g., a main memory bus) couples north bridge 909 of chipset 903 to main memory 902. Communication bus 993 (e.g., the Advanced Graphics Port interface) couples north bridge of chipset 903 to graphic subsystem 910. Communication buses 994, 995 and 997 (e.g., a PCI bus) couple south bridge 905 of chip set 903 to removable data storage device 904, input device 907, signal communications port 908 respectively. Graphics subsystem 910 includes graphics processor 911 and frame buffer 915.

The components of computer system 900 cooperatively operate to provide versatile functionality and performance. In one exemplary implementation, the components of computer system 900 cooperatively operate to provide predetermined types of functionality. Communications bus 991, 992, 993, 994, 995 and 997 communicate information. Central processor 901 processes information. Main memory 902 stores information and instructions for the central processor 901. Removable data storage device 904 also stores information and instructions (e.g., functioning as a large information reservoir). Input device 907 provides a mechanism for inputting information and/or for pointing to or highlighting information on display 920. Signal communication port 908 provides a communication interface to exterior devices (e.g., an interface with a network). Display device 920 displays information in accordance with data stored in frame buffer 915. Graphics processor 911 processes graphics commands from central processor 901 and provides the resulting data to video buffers 915 for storage and retrieval by display monitor 920.

FIG. 10 shows another exemplary architecture that incorporates an exemplary video processor or graphics processor in accordance with one embodiment of the present invention. As depicted in FIG. 10, system 1000 embodies a programmable SOC integrated circuit device 1010 which includes a two power domains 1021 and 1022. The power domain 1021 includes an “always on” power island 1031. The power domain 1022 is referred to as the core of the SOC and includes a CPU power island 1032, a GPU power island 1033, a non-power gated functions island 1034, and an instance of the video processor. The FIG. 10 embodiment of the system architecture 1000 is targeted towards the particular intended device functions of a battery-powered handheld SOC integrated circuit device. The SOC 1010 is coupled to a power management unit 1050, which is in turn coupled to a power cell 1051 (e.g., one or more batteries). The power management unit 1050 is coupled to provide power to the power domain 1021 and 1022 via the dedicated power rail 1061 and 1062, respectively. The power management unit 1050 functions as a power supply for the SOC 1010. The power management unit 1050 incorporates power conditioning circuits, voltage pumping circuits, current source circuits, and the like to transfer energy from the power cell 1051 into the required voltages for the rails 1061-1062.

In the FIG. 10 embodiment, the video processor is within the domain 1022. The video processor provides specialized video processing hardware for the encoding of images and video. As described above, the hardware components of the video processor are specifically optimized for performing real-time video encoding. The always on power island 1031 of the domain 1021 includes functionality for waking up the SOC 1010 from a sleep mode. The components of the always on domain 1021 will remain active, waiting for a wake-up signal. The CPU power island 032 is within the domain 1022. The CPU power island 1032 provides the computational hardware resources to execute the more complex software-based functionality for the SOC 1010. The GPU power island 1033 is also within the domain 1022. The GPU power island 1033 provides the graphics processor hardware functionality for executing 3-D rendering functions.

FIG. 11 shows a diagram showing the components of a handheld device 1100 in accordance with one embodiment of the present invention. As depicted in FIG. 11, a handheld device 1100 includes the system architecture 1000 described above in the discussion FIG. 10. The handheld device 1100 shows peripheral devices 1101-1107 that add capabilities and functionality to the device 1100. Although the device 1100 is shown with the peripheral devices 1101-1107, it should be noted that there may be implementations of the device 1100 that do not require all the peripheral devices 1101-1107. For example, in an embodiment where the display(s) 1103 are touch screen displays, the keyboard 1102 can be omitted. Similarly, for example, the RF transceiver can be omitted for those embodiments that do not require cell phone or WiFi capability. Furthermore, additional peripheral devices can be added to device 1100 beyond the peripheral devices 1101-1107 shown to incorporate additional functions. For example, a hard drive or solid state mass storage device can be added for data storage, or the like.

The RF transceiver 1101 enables two-way cell phone communication and RF wireless modem communication functions. The keyboard 1102 is for accepting user input via button pushes, pointer manipulations, scroll wheels, jog dials, touch pads, and the like. The one or more displays 1103 are for providing visual output to the user via images, graphical user interfaces, full-motion video, text, or the like. The audio output component 904 is for providing audio output to the user (e.g., audible instructions, cell phone conversation, MP3 song playback, etc.). The GPS component 1105 provides GPS positioning services via received GPS signals. The GPS positioning services enable the operation of navigation applications and location applications, for example. The removable storage peripheral component 1106 enables the attachment and detachment of removable storage devices such as flash memory, SD cards, smart cards, and the like. The image capture component 1107 enables the capture of still images or full motion video. The handheld device 1100 can be used to implement a smart phone having cellular communications technology, a personal digital assistant, a mobile video playback device, a mobile audio playback device, a navigation device, or a combined functionality device including characteristics and functionality of all of the above.

Thus, the present systems and methods facilitate enhanced image presentation in an efficient and effective manner. Direct and indirect lighting calculations can be performed by different systems which in turn facilitates increased image presentation results on a variety of systems (e.g., clients, end user devices, mobile devices, etc.). In addition, various global and indirect lighting calculation results can be amortized over a variety of different systems or clients. A variety of indirect lighting representations and compression techniques can be utilized including separating view-independent and view-dependent computations between GPUs and repurposing video codec (e.g., such as H.264 for irradiance map compression, etc.).

Some portions of the detailed descriptions are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means generally used by those skilled in data processing arts to effectively convey the substance of their work to others skilled in the art. A procedure, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps include physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, optical, or quantum signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present application, discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining”, “displaying” or the like, refer to the action and processes of a computer system, or similar processing device (e.g., an electrical, optical, or quantum, computing device), that manipulates and transforms data represented as physical (e.g., electronic) quantities. The terms refer to actions and processes of the processing devices that manipulate or transform physical quantities within a computer system's component (e.g., registers, memories, other such information storage, transmission or display devices, etc.) into other data similarly represented as physical quantities within other components.

The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the Claims appended hereto and their equivalents. The listing of steps within method claims do not imply any particular order to performing the steps, unless explicitly stated in the claim. 

1. A network, comprising: a first system configured to perform a first portion of lighting calculations for an image and combing results of the first portion of lighting calculations for the image with results of a second portion of lighting calculations; and a second system configured to perform the second portion of lighting calculations and forward the results of the second portion of the lighting calculations to the first system.
 2. The network of claim 1, wherein the second portion of lighting calculations is associated with indirect lighting calculations.
 3. The network of claim 1, wherein the first portion of lighting calculations is associated with direct lighting calculations.
 4. The network of claim 1, wherein the first system is in a local location and the second system is in a remote location.
 5. The network of claim 1, wherein the first system is a client.
 6. The network of claim 1, wherein the second system is a server.
 7. The network of claim, 1 wherein the second system is in a cloud computing environment.
 8. The network of claim 1, wherein the first system and the second system is in a cloud computing environment and a video including the image is transmitted to a local system.
 9. The network of claim 1, wherein the results of the second portion of lighting calculations are transmitted to a third or more systems and combined with a plurality of results of other portions of lighting calculations performed by the third or more systems.
 10. The network of claim 1, wherein the results of the second portion of lighting calculations include Voxel results and the Voxel results are combined with the first lighting calculation results on the first system.
 11. The network of claim 1, wherein the results of the second portion of lighting calculations include irradiance map results and the irradiance map results are combined with the first lighting calculation results on the first system.
 12. The network of claim 1, wherein the results of the second portion of lighting calculations include photon results and the photon results are combined with the first lighting calculations results on the first system.
 13. The network of claim 1, wherein various streaming approaches are implemented to improve latency.
 14. The network of claim 1, wherein the first portion of lighting calculations and the second portion of lighting calculations are not synchronized.
 15. A method of performing lighting calculations comprising: performing a first portion of lighting calculations on a first system at a local location, wherein the lighting calculations are associated with an image; performing a second portion of lighting calculations on a second system at a remote location, wherein the lighting calculations are associated with the image; communicating the first portion of the lighting calculated to the first system at the local location; and combining the first portion of the lighting calculations with the second portion of the lighting calculations, wherein the combining is performed on the first system at the local location.
 16. The method of claim 15, wherein the second portion of lighting calculations is associated with indirect lighting calculation and the first portion of lighting calculations is associated with direct lighting calculations.
 17. The method of claim 15, wherein the first system is a client and the second system is a server.
 18. The method of claim 15, wherein the remote location is in a cloud computing environment.
 19. The method of claim 15, wherein the results of the second portion of lighting calculations are amortized among a plurality of additional systems at other locations.
 20. A system comprising a memory configured to store instructions and a processor configured to perform operations in accordance with the instructions, wherein the instructions comprise: performing a first portion of lighting calculations for an image; receiving results of a second portion of lighting calculations for the image, wherein the second portion of the lighting calculations are performed by another system; and combining the first portion of the lighting calculations with the second portion of the lighting calculations as part of rendering the image. 